Skip to content

release: v0.1.1 - #39

Merged
prashar32 merged 1 commit into
mainfrom
release/v0.1.1
May 31, 2026
Merged

release: v0.1.1#39
prashar32 merged 1 commit into
mainfrom
release/v0.1.1

Conversation

@prashar32

Copy link
Copy Markdown
Owner

Release prep for v0.1.1 — the version markers that don't auto-update (CLAUDE.md §13).

What's in v0.1.1

(Also merged since v0.1.0 but not user-facing, so not in the changelog: #36 skip auto-review on fork PRs.)

Marker bumps

File Change
CHANGELOG.md [Unreleased] → dated [0.1.1]; fresh empty [Unreleased]; compare links
docs/VISION.md status line → v0.1.1 (released)
internal/version/version.go default 0.1.0-dev0.1.2-dev (stamped real via -ldflags)
sdks/python pyproject.toml + __init__.__version__0.1.1

After merge (tagging is manual — your call)

  1. git tag -a v0.1.1 -m "v0.1.1" && git push origin v0.1.1 → release workflow builds + cosign-signs the multi-arch GHCR image and GoReleaser binaries.
  2. Verify: docker run ghcr.io/prashar32/riskkernel:0.1.1 version and cosign verify ….

Not in this release (queued for v0.1.2)

#34 (halt status persistence), #35 (audit json tags — contributor PR), govulncheck toolchain bump, #37/#38 (usage rollup / tool_calls read API), and the two minor nits.

Roll [Unreleased] into [0.1.1] and bump the version markers (CLAUDE.md §13):
- CHANGELOG: dated [0.1.1] section (examples demo + SDK empty-wheel fix #32);
  fresh empty [Unreleased]; compare links updated.
- docs/VISION.md: status line → v0.1.1 (released).
- internal/version/version.go: default → 0.1.2-dev (releases stamp the real
  version via -ldflags; this only shows on un-stamped local builds).
- sdks/python: pyproject + __init__ __version__ → 0.1.1.
@prashar32
prashar32 merged commit 941b123 into main May 31, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant